11. GPRS Commands > 11.11 AT+CGQREQ   Quality of Service Profile (Requested)

11.11
AT+CGQREQ   Quality of Service Profile (Requested)
Syntax
Test Command  
Response(s)
+CGQREQ: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)
Read Command  
Response(s)
Write Command  
Response(s)
Reference(s) 
PIN 
ASC0 
ASC1 
USB 
MUX1 
MUX2 
MUX3 
Charge 
Last 
GSM 07.07

Command Description
The test command returns values supported as a compound value. If the MT supports several PDP types, the parameter value ranges for each PDP type are returned on a separate line.
The read command returns the current settings for each defined context.
This command allows the TE to specify a Quality of Service Profile that is used when the MT sends an Activate PDP Context Request message to the network.
The set command specifies a profile for the context identified by the (local) context identification parameter, <cid>.
A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid> to become undefined.
AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.

Parameter Description
 
<cid>(num)
Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands.
1...2
 
 
Precedence class
[0]
network subscribed value
1
High Priority
Service commitments shall be maintained ahead of precedence classes 2 and 3
2
Normal priority
Service commitments shall be maintained ahead of precedence class 3
3
Low priority
Service commitments shall be maintained
 
<delay>(num)
Delay class
This parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRS network(s).
[0]
network subscribed value
1..4
with SDU size = 128 octets:
 

with SDU size = 1024 octets:
 
 
Reliability class
[0]
network subscribed value
1
Non real-time traffic, error-sensitive application that cannot cope with data loss
2
Non real-time traffic, error-sensitive application that can cope with infrequent data loss
3
Non real-time traffic, error-sensitive application that can cope with data loss, GMM/SM, and SMS
4
Real-time traffic, error-sensitive application that can cope with data loss
5
Real-time traffic, error non-sensitive application that can cope with data loss
 
<peak>(num)
Peak throughput class
in octets per second
[0]
network subscribed value
1
Up to 1 000 (8 kbit/s)
2
Up to 2 000 (16 kbit/s)
3
Up to 4 000 (32 kbit/s)
4
Up to 8 000 (64 kbit/s)
5
Up to 16 000 (128 kbit/s)
6
Up to 32 000 (256 kbit/s)
7
Up to 64 000 (512 kbit/s)
8
Up to 128 000 (1024 kbit/s)
9
Up to 256 000 (2048 kbit/s)
 
<mean>(num)
Mean throughput class
in octets per hour
[0]
network subscribed value
1
100 (~0.22 bit/s)
2
200 (~0.44 bit/s)
3
500 (~1.11 bit/s)
4
1 000 (~2.2 bit/s)
5
2 000 (~4.4 bit/s)
6
5 000 (~11.1 bit/s)
7
10 000 (~22 bit/s)
8
20 000 (~44 bit/s)
9
50 000 (~111 bit/s)
10
100 000 (~0.22 kbit/s)
11
200 000(~0.44 kbit/s)
12
500 000(~1.11 kbit/s)
13
1 000 000 (~2.2 kbit/s)
14
2 000 000 (~4.4 kbit/s)
15
5 000 000 (~11.1 kbit/s)
16
10 000 000 (~22 kbit/s)
17
20 000 000 (~44 kbit/s)
18
50 000 000 (~111 kbit/s)
31
best effort
 
Packet Data Protocol type
“IP“
 


Notes
•
•

Example

If some of the QoS parameters are omitted, they will keep their current value (or the default value if not specified so far), e.g.: